Gravity Forms Authorize.Net Add-On v2.0 is now available via automatic update and the Add-On Downloads page.
This is a major maintenance release that includes migration of the codebase to the Gravity Forms Add-On Framework. Subscription handling has also been improved and streamlined.
Note: The Authorize.Net Add-On is available to Gravity Forms Developer License customers.
What's New
- Codebase migrated to utilize Gravity Forms Add-On Framework.
- Updated subscription so that extra "voided" transaction is no longer created.
Don't own a Gravity Forms Developer license? Upgrade or Purchase one now!
Please Note: Automatic Update will only work if you have entered a valid Developer License Key in the Settings page of Gravity Forms in your WordPress Administration Panel.
You may download the Authorize.Net Add-On here, and read the documentation here.
Share This
Will you guys be upgrading the API URLs soon to accommodate for the new endpoints that were announced by Authorize.net recently?
http://www.authorize.net/support/akamaifaqs
Thanks! 🙂
I'll have the support team take a look at the Authorize.Net API updates and see how they can be utilized in our Add-On.
Thanks 502, I had the same question when coming here.
So our lead developer is aware of the new Akamai endpoints for Authorize.Net. They haven't been implemented just yet as we utilize Authorize.Net's official PHP wrapper for API interaction and the PHP wrapper hasn't been updated yet to support these changes. I have reached out to Authorize.Net to see when they'll be updating the PHP wrapper to support it.
Carl, thanks for the update. Is it safe to assume that the PHP wrapper changes will happen within the plugin and an update will be pushed? Should I keep checking back here to see when this is ready? We have a few clients using Authorize.net that want to make sure this will work when the old endpoints are deprecated. Thanks!
Yes, we'll release an update to the Authorize.Net Add-On when that occurs. But from what I understand from the Authorize.Net team the existing endpoints won't be deprecated in a way that they won't work. They'll automatically forward to the new Akamai endpoints when/if the deprecation occurs for backwards compatibility.